Hide the Guardex lock registry from repo change rows#281
Merged
Conversation
added 2 commits
April 22, 2026 11:09
Synthetic gitguardex-agent://<sanitized-branch> URIs let the Active Agents view decorate session rows without pointing at workspace files. The refresh path now invalidates both tree data and session decorations, and the focused tests cover URI assignment plus the 10 minute and 30 minute idle thresholds. Constraint: Session rows are not backed by real files, so the decoration key must be synthetic and branch-stable Constraint: Working rows must keep their existing styling Rejected: Reuse workspace file URIs for session rows | would couple session decoration to unrelated files Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep vscode/guardex-active-agents/extension.js and templates/vscode/guardex-active-agents/extension.js mirrored when session-row UI changes Tested: node --test test/vscode-active-agents-session-state.test.js; openspec validate agent-codex-vscode-tree-lock-decorations-2026-04-22-10-55 --type change --strict Not-tested: npm test hangs in test/install.test.js while autofinish flows are spawned
The active-agents session-schema tests on current main already expect .omx/state/agent-file-locks.json to stay out of the CHANGES section. Filtering that path in the runtime and template schema keeps the existing lock-registry rows green without changing the idle session decoration behavior. Constraint: The lock registry is Guardex metadata, not a user edit, so showing it in repo change rows creates noisy false positives Rejected: Skip the existing lock-registry assertions | would leave the focused extension test file red on current main Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep metadata files out of repo-root change lists unless the companion explicitly needs to surface them Tested: node --test test/vscode-active-agents-session-state.test.js Not-tested: npm test still hangs in test/install.test.js while autofinish flows are spawned
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated by scripts/agent-branch-finish.sh (PR flow).